-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution][RAC] Fixes Threshold Rule functionality for post-rule-migration 8.0 #117571
Conversation
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/security-solution (Team: SecuritySolution) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes LGTM! Can you add a couple more sentences to the PR to add some details about what's being fixed here and how it behaves before and after the fix?
* Remove unused code * Fix threshold field refs * Fix import * UI fixes for Rules * Threshold Cypress test fixes * Type fixes * Threshold signal test fixes * Handle legacy schema optionally * Fix threshold integration test * More test fixes
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Thanks @marshallmain ... done! |
* Remove unused code * Fix threshold field refs * Fix import * UI fixes for Rules * Threshold Cypress test fixes * Type fixes * Threshold signal test fixes * Handle legacy schema optionally * Fix threshold integration test * More test fixes Co-authored-by: Madison Caldwell <[email protected]>
Summary
Threshold rules were broken after merging #112113 because the UI was referencing the
signal.*
fields, whereas new alerts are generated using the AAD schema. Additionally, threshold alerts were being generated incorrectly, placingthreshold.result
at the top level of the document instead of underkibana.alert.threshold_result
where it belongs.This PR:
kibana.alert.threshold_result
)nonEcsData
,getFilterAndRuleBounds
)signal.*
fieldsChecklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers